Method and system for rapidly starting up an IEEE 1394 network

ABSTRACT

According to one embodiment of the invention, a network system for carrying control data between a controller and a device to be controlled is provided. The network system comprises a bus system operable to carry data between the controller and the device according to an IEEE 1394 standard. The IEEE 1394 standard defines a start up operation that includes one or more sequences. The bus system is also operable to perform a modified start up operation that excludes at least one of the sequences of the start up operation defined by the IEEE 1394 standard.

TECHNICAL FIELD OF THE INVENTION

This invention relates generally to electronics and more particularly toa method and system for rapidly starting up an IEEE 1394 network.

BACKGROUND OF THE INVENTION

IEEE 1394 is an electronics standard for connecting devices to otherdevices or to a microprocessor of a computer. A network or a bus thatcomplies with the IEEE 1394 standard is referred to as an “IEEE 1394network” or an “IEEE 1394 bus.” An IEEE 1394 bus may accommodate up to63 devices with data transfer speeds of up to 3.2 Gigabits per second.The flexibility and large bandwidth of an IEEE 1394 bus makes the IEEE1394 bus ideal for consumer electronics and multimedia applications. Twowell-known implementations of IEEE 1394 are trademarked as APPLE'sFIREWIRE and SONY's i-LINK.

Command and control applications, such as drive-by-wire, may benefitfrom an IEEE 1394 bus's flexibility and capabilities. Drive-by-wirerefers to a method of controlling components of an automobile using acomputer rather than a mechanical linkage. Implementing an IEEE 1394 busin command and control applications has been challenging. For example,whereas command and control applications generally require the controlnetwork to start up within approximately 100 microseconds, an IEEE 1394bus generally requires approximately 500 milliseconds to start up. Sucha relatively long start up time may compromise the performance of thecontrolled device in a command and control application. For example, ifa control network of an electronically-modulated braking system of anautomobile had a relatively long start up time, the time delay betweenwhen an operator steps on the brake pedal and when the brakes areactually applied may be too long and result in an accident.

SUMMARY OF THE INVENTION

According to one embodiment of the invention, a network system forcarrying control data between a controller and a device to be controlledis provided. The network system comprises a bus system operable to carrydata between the controller and the device according to an IEEE 1394standard. The IEEE 1394 standard defines a start up operation thatincludes one or more sequences. The bus system is also operable toperform a modified start up operation that excludes at least one of thesequences of the start up operation defined by the IEEE 1394 standard.

Some embodiments of the invention provide numerous technical advantages.Other embodiments may realize some, none, or all of these advantages.For example, according to one embodiment, the start up time of an IEEE1394 bus system is reduced by skipping one or more sequences that areincluded in the start up procedure defined by the IEEE 1394 standard. Inanother embodiment, command and control applications, such asdrive-by-wire, may benefit from the flexibility and fast data transferrate of an IEEE 1394 bus system without suffering from a relatively longstart up time. In another embodiment, where an IEEE 1394 bus implementedas an optical network, the probability of erroneous data detection isreduced by skipping one or more sequences of the start up procedure thatmay contribute to the erroneous data detection.

Other advantages may be readily ascertainable by those skilled in theart.

BRIEF DESCRIPTION OF THE DRAWINGS

Reference is now made to the following description taken in conjunctionwith the accompanying drawings, wherein like reference numbers representlike parts, in which:

FIG. 1 is a schematic diagram illustrating one embodiment of a commandand control system that may benefit from the teachings of the presentinvention;

FIG. 2 is a block diagram illustrating one embodiment of a controlsystem shown in FIG. 1; and

FIG. 3 is a block diagram illustrating one embodiment of a method forrapidly starting up an IEEE 1934 network.

DETAILED DESCRIPTION OF EXAMPLE EMBODIMENTS OF THE INVENTION

Embodiments of the invention are best understood by referring to FIGS. 1through 3 of the drawings, like numerals being used for like andcorresponding parts of the various drawings.

FIG. 1 is a schematic diagram illustrating one embodiment of a commandand control system 10 that may benefit from the teachings of the presentinvention. As shown in FIG. 1, system 10 is an automobile. Forillustrative purposes, system 10 is referred to herein as automobile 10;however, any mechanical, electrical, or electromechanical system thatincludes one or more devices that may be controlled electronically maybe system 10.

Referring again to FIG. 1, automobile 10 comprises an engine 14, a brakesystem 18, a control unit 20, a brake pedal 28, and a gas pedal 30.Brake system 18 and engine 14 are coupled to brake pedal 28 and gaspedal 30 through control unit 20. Engine 14 is operable to provide thedrive power necessary to move automobile 10 and operate the variouscomponents of automobile 10. Brake system 18 is operable to apply abraking force to stop automobile 10.

Control unit 20 is operable to receive input from a driver 34 throughpedals 28 and 30, and provide corresponding output signals to engine 14and/or brake system 18 to implement the commands from driver 34. Controlunit 20 may be operable to decide how to react to a particular inputtransmitted from pedals 28 and/or 30 by receiving input from engine 14and/or brake system 18 and analyzing all the received input according toa control algorithm. For example, where control unit 20 is operable toconduct engine management, control unit 20 may be operable to optimizeengine performance of engine 14 by controlling the fuel and air mixtureof engine 14 depending on the amount of air available to engine 14,engine temperature, and the speed and the extent to which gas pedal 30is pressed. In another example where control unit 20 is operable toelectronically modulate brake system 18, control unit 20 may receiveinput from brake pedal 28, and depending on how much and how fast brakepedal 30 is pressed, apply an appropriate braking force through brakesystem 18. In some embodiments, control unit 20 may be operable to slowdown engine 14 in conjunction with the application of braking forcethrough brake system 18 in response to a particular input received fromdriver 34 through brake pedal 28. Control unit 20 and a device to becontrolled, such as engine 14 or brake system 18, are referred to hereinas a control system 24.

A control unit for controlling a device, such as an engine, generallyincludes a control bus that couples a microprocessor of the control unitto the device to be controlled. In command and control applications,such as control system 24 shown in FIG. 1, the response time betweenwhen a command is received at a control unit and when the appropriateoutput is transmitted to a controlled device in response to the receivedcommand may be important for a timely execution of the command. Forexample, a control unit designed to control a brake system of anautomobile may experience an error during operation and reset itself.When the control unit resets itself, a bus system of a control busconnecting the brake system to the microprocessor of the control unitmay be required to perform a start up procedure (also referred to as astart up operation). If the start up time of the control bus is toolong, and brakes were applied during such a start up, the brake systemmay not be activated quickly enough. Such a delay may lead to accidents.Because of such scenarios, command and control applications generallyrequire a start up time of approximately 100 microseconds or less forits control buses.

An IEEE 1394 bus system, which includes an IEEE 1394 bus and a buscontroller, may offer a large bandwidth for faster data transmission andother capabilities that may be desirable in a command and controlapplication. But an IEEE 1394 bus system is not commonly implemented forcertain types of command and control applications because the start upof an IEEE 1394 bus is too slow unless redundant networks are used. TheIEEE 1394 standard defines a start up procedure for an IEEE 1394 bussystem to perform for an IEEE 1394 bus prior to assuming an activenetwork status. The start up procedure may include a debounce delaysequence, a speed negotiation sequence, a training and symbolsynchronization sequence, and a bus initialization sequence. The IEEE1394 standard, such as IEEE 1394b-2002 and 1394a-2000, is incorporatedherein by reference. An IEEE 1394 bus system may also perform a deviceinitialization sequence in conjunction with the start up procedure. Thedevice initialization sequence may vary depending on the particularvendor of the IEEE 1394 bus system.

The device initialization sequence is a sequence where the device isinitialized to a known state. The time required to perform this sequencemay vary based on the design but can be as short as a few microseconds.The debounce delay sequence is a sequence that enables a bus to delayinforming a processor of a computer regarding a break in connectionbetween a bus and a controlled device. This may be necessary for the“hot plug” capability of a bus because such a delay may prevent theprocessor from reading the device until the connection of a new deviceis completed. In general, the performance of the debounce delay sequencerequires approximately 320 milliseconds. The speed negotiation sequenceis a sequence that enables a processor and a controlled device tonegotiate an appropriate communications speed. This may be necessary forthe “hot plug” capability of a bus because different devices that may beplugged into a bus may be designed to communicate at different speeds,which may require a processor to agree on an operating speed with eachconnected device. Generally, the performance of the speed negotiationsequence requires approximately 84 to 168 milliseconds. Training andsymbol synchronization sequence is a sequence where 10 bit symbols areexchanged and the node aligns to the beginning of these 10 bit symbols.Performing this sequence generally requires approximately 20-30microseconds to perform but can be longer depending on certain factors,such as noise and the length of connection. The bus initializationsequence comprises a bus reset and a self-identification process.Performing the bus initialization sequence may require approximately 250microseconds for a long bus reset to approximately 80 microseconds orless for a short bus reset. Factors, such as the number of nodes on thebus and thus the number of self-identification packets, may determinethe actual time required to perform the bus initialization sequence.Performing the start up procedure by an IEEE 1394 bus system may requireapproximately 500 milliseconds, which is too slow compared to theapproximately 100 microsecond requirement of a command and controlapplication.

Implementing an optical network in accordance with the IEEE 1394standard generally requires additional circuitry to account for possiblefalse detection of data. False detection may occur because of thefollowing. In general, the sensitivity of an optical network may have atendency to increase when the network is not carrying signals. Forexample, an optical network may not carry signals during the time priorto the start up of the optical network. However, when the start upprocedure defined by the IEEE 1394 standard is performed, an opticalnetwork may be required to exchange signals between nodes to identifyand maintain connections between nodes. For example, each node of anoptical network may transmit and expect to receive a signal from anothernode at 42 millisecond intervals. The frequency of signal transmissionmay increase if the optical network is performing a speed negotiationsequence. Because of the increased sensitivity of the optical networkprior to the start up procedure, these signals for identifyingconnections and negotiating speed during the start up procedure may beinterpreted as data. To compensate for this, additional circuitry maynecessary to either filter out these signals exchanged during the startup procedure or to avoid false detection of these signals as data.

According to one embodiment of the present invention, a method andsystem for rapidly starting up an IEEE 1394 bus is provided by modifyinga bus controller that controls the IEEE 1394 bus to skip one or moresequences that are included in the start up procedure defined by theIEEE 1394 standard. Skipping one or more sequences that may not need tobe performed in a command and control application shortens the start uptime of an IEEE 1394 bus, which allows the command and controlapplication to benefit from the capabilities of the IEEE 1394 bus systemwhile avoiding the problems associated with a relatively slow start up.In one embodiment, skipping one or more sequences simplifies thesupporting circuitry of an optical IEEE 1394 network.

FIG. 2 is a block diagram illustrating one embodiment of control system24 shown in FIG. 1. As described above in conjunction with FIG. 1,system 24 includes control unit 20 coupled with controlled system 14,such as engine 14. Although engine 14 is used as an example in system24, any device or a combination of devices that may be controlledelectronically may be system 14. Control unit 20 includes a processor100 coupled to a bus system 114 and a memory 108 storing a controlprogram 104. Bus system 114 includes a bus 110 and a bus controller 112.Processor 100 is operable to access and execute program 104 stored inmemory 108 and to control system 14 through bus 110. When executingprogram 104, processor 100 is operable to receive input from an operatorthrough one or more signal actuators, such as pedals 28 and 30 shown inFIG. 1, and transmit appropriate control signals to controlled system 14through bus 110 according to the instructions of program 104. Forexample, when gas pedal 30 is abruptly pressed down all the way,processor 100 may receive an input indicating that action from gas pedal30, and transmit a control signal to engine 14 indicating that a maximumamount of air and gas should be injected into the combustion chambers ofengine 14 to produce maximum power. Processor 100 may be coupled to morethan one device or systems that are controlled according to program 104.Examples of processor 100 include PENTIUM processors available fromINTEL Corporation. While the command and control functions are describedas being initiated from processor 100, other devices in other locationsmay also initiate portions or all of the command and control functions.

Bus system 114 is operable carry signals according to a protocol definedin IEEE 1394 standard. In one embodiment, IEEE 1394 standard refers to anetwork standard defining a start up procedure that includes at leastone sequence associated with a “hot plug” capability, a “plug-and-play”capability, or any other analogous capability. Examples of the IEEE 1394standard include IEEE 1394b-2002 standard and IEEE 1394a-2000 standard.In one embodiment, bus system 114 is an IEEE 1394 bus system where buscontroller 112 has been modified to skip the debounce delay sequenceand/or the speed negotiation sequence when performing the start upprocedure defined by the IEEE 1394 standard. Such a start up procedureis referred to as a modified start up procedure or a modified start upoperation. Both the debounce delay sequence and the speed negotiationsequence are associated with the hot plug and/or plug-and-playcapability of IEEE 1394 standard, which may not be needed in a commandand control environment because a control network of a command andcontrol application is generally a fixed network.

A “fixed network” refers to a network that accepts only devices havingfixed operating speeds, or that does not allow an exchange of deviceswhile the system is not in operation. Because command and controlapplications use fixed networks, command and control applications maynot need the hot plug or the plug-and-play capabilities. As such, theone or more sequences of the IEEE 1394 start up procedure that areassociated with the hot plug and/or plug-and-play capabilities may beskipped while performing the start up procedure for command and controlapplications. By skipping these sequences, command and controlapplications may benefit from the advantages associated with an IEEE1394 bus system without suffering from the problems associated with aslow start up time. In one embodiment, a command and control network mayhave fixed segments that may operate at different speeds. For example,some segments having optical fiber may operate at 200 megabits persecond while other segments having copper connections may operate at 400megabits per second or 800 megabits per second. Such embodiments mayalso benefit from the teachings of the present invention.

In one embodiment, IEEE 1394 bus system 114 is operable to skip thedebounce delay sequence. In one embodiment, IEEE 1394 bus system 114 isoperable to skip the debounce delay sequence, the speed negotiationsequence, and any other sequence that may be associated with afunctionality of an IEEE 1394 bus system that is not required in aparticular command and control application in which IEEE 1394 bus system114 is used.

In one embodiment where bus system 114 is an IEEE 1394b-2002 bus system,sequences such as the debounce delay sequence and the speed negotiationsequence may be skipped. In one embodiment where bus system 114 is anIEEE 1394a-2000 bus system, the debounce delay sequence may be skipped.In such an embodiment, the speed negotiation sequence is not an issuebecause IEEE 1394a-2000 standard does not include a speed negotiationsequence. In one embodiment, any one or more of the sequences that arenot needed in a particular application may be skipped by bus system 114.By skipping one or more sequences of a start up procedure defined by theIEEE 1394 standard, IEEE 1394 bus system 114 may require approximately100 microseconds or less to start up, which complies with the start uprequirements of many command and control applications. In someembodiments, even if skipping one or more sequences results in a startup time that is greater than 100 microseconds, a reduction of the startup time from the skipping of one or more sequences may facilitate theuse of IEEE 1394 bus system 114 in command and control applications.

Bus controller 112 of bus system 114 may be configured to perform amodified start up procedure using any suitable method. In oneembodiment, bus system 114 may be implemented as a state machine.Although bus 110 and bus controller 112 have been shown in FIG. 2 as bussystem 114 that is separate from CPU 100, in some embodiments, buscontroller 112 may be implemented as part of CPU 100.

In one embodiment, bus 110 may be an optical network that complies withIEEE 1394 standard. An optical network may be suitable in someapplications where electromagnetic interference from a copper-basednetwork may be undesirable in an application. In such embodiments wherethe network is an optical bus, skipping the debounce delay sequenceand/or speed negotiation sequence may advantageous because the adjacentcircuitry of optical network bus 110 may be simplified. This is becausewhen the debounce delay sequence and the speed negotiation sequence areskipped, the signaling activity for maintaining a connection between thenodes of optical network bus 110 and the signaling activity for speednegotiation are not necessary. Thus, the probability of false datadetection is lowered, which may eliminate the need for additionalcircuitry that is designed to minimize the false detection of data.

FIG. 3 is a block diagram illustrating one embodiment of a method 150for rapidly starting up an IEEE 1394 network. For illustrative purposes,the features shown in FIGS. 1 and 2 are used as devices implementing thevarious acts of method 150. However, any suitable device or combinationof devices may be used to implement the acts of method 150.

Method 150 starts at step 156. At step 158, bus system 114 initiates aparticular type of device initialization sequence depending on theparticular vendor of bus system 114. At step 160, bus system 114 skipsthe debounce delay sequence of the start up procedure defined in IEEE1394 standard. At step 164, bus system 114 skips the speed negotiationsequence of the start up procedure defined in the IEEE 1394 standard. Insome embodiments, either step 160 or step 164 may be omitted. At step166, bus system 114 performs the bus initialization sequence of thestart up procedure defined in the IEEE 1394 standard. In someembodiments, step 166 may be omitted. At step 168, active data exchangeis performed using bus 110 in accordance with IEEE 1394 standard. In oneembodiment, bus system 114 may require approximately 80-250 microsecondsto perform the bus initialization sequence in accordance with the IEEE1394 standard. In one embodiment, the debounce delay sequence of step160 may require approximately 320 milliseconds to be performed by bussystem 114. In one embodiment, the speed negotiation sequence of step164 may require approximately 84 to 168 milliseconds to be performed bybus system 114. Method 150 stops at step 170.

Although some embodiments of the present invention have been describedin detail, it should be understood that various changes, substitutions,and alterations can be made hereto without departing from the spirit andscope of the invention as defined by the appended claims.

1. A control system, comprising: a system operable to be controlledelectronically over a network, the system requiring the network to startup within approximately 100 microseconds; a processor coupled to thesystem, the processor operable to execute a program operable to controlthe system; a bus system coupled to the system and the processor, thebus system operable to carry control data between the system and theprocessor according to an IEEE 1394 standard, the IEEE 1394 standarddefining a start up operation that includes a bus initializationsequence, a debounce delay sequence, a speed negotiation sequence, and atraining and symbol synchronization sequence, the bus system operable toperform a modified start up operation that includes the businitialization sequence and the training and symbol synchronizationsequence but excludes the debounce delay sequence and the speednegotiation sequence.
 2. The control system of claim 1, wherein the bussystem comprises an optical network.
 3. The control system of claim 1,wherein the debounce delay sequence requires approximately 320milliseconds to be performed by the bus system, and the speednegotiation sequence requires approximately 84 milliseconds toapproximately 168 milliseconds to be performed by the bus system.
 4. Thecontrol system of claim 1, wherein the system is an engine and theprogram is operable to control the engine by optimizing a performancemeasure of the engine.
 5. A network system for carrying control databetween a controller and a device to be controlled, the network systemcomprising: a bus system operable to: carry data between the controllerand the device according to an IEEE 1394 standard, the IEEE 1394standard defining a start up operation that includes one or moresequences; and perform a modified start up operation that excludes atleast one of the sequences of the start up operation defined by the IEEE1394 standard.
 6. The network system of claim 5, wherein the bus systemcomprises a bus, and further comprising a system coupled to the bussystem and operable to be controlled electronically over the bus, thesystem requiring the bus system to start up within a time period lessthan 500 milliseconds.
 7. The network system of claim 5, wherein the bussystem comprises a bus, and further comprising a system coupled to thebus system and operable to be controlled electronically over the bus,the system requiring the bus system to start up within a time periodequal to or less than approximately 100 microseconds.
 8. The networksystem of claim 5, wherein the one or more sequences comprise a debouncedelay sequence, a speed negotiation sequence, a training andsynchronization sequence, and a bus initialization sequence, and the atleast one of the sequences comprise the debounce delay sequence and thespeed negotiation sequence but not the training and synchronizationsequence and the bus initialization sequence.
 9. The network system ofclaim 5, wherein the bus system comprises a bus, and further comprising:a system coupled to the bus system and operable to be controlledelectronically over the bus, the system requiring the bus system tostart up within a time period less than 100 microseconds; and whereinthe bus system is operable to receive a plurality of devices each havinga different operating speed that is fixed when coupled to the bussystem.
 10. The network system of claim 5, wherein the one or moresequences comprise a bus initialization sequence, a debounce delaysequence, and a speed negotiation sequence, and the at least one of thesequences comprise the debounce delay sequence and the speed negotiationsequence but does not include the bus initialization sequence.
 11. Thenetwork system of claim 5, wherein the at least one sequence requires atleast 499.9 milliseconds to be performed by the bus system.
 12. Thenetwork system of claim 5, and further comprising an engine of anautomobile coupled to the bus system, the engine operable to becontrolled electronically over the bus, the engine requiring the bussystem to start up within a time period equal to or less thanapproximately 100 microseconds; wherein the one or more sequencescomprise a bus initialization sequence, a debounce delay sequence, and aspeed negotiation sequence, and the at least one of the sequencescomprise the debounce delay sequence and the speed negotiation sequencebut does not include the bus initialization sequence; and wherein thedebounce delay sequence and the speed negotiation sequence togetherrequire up to 499.9 milliseconds to be performed by the bus system. 13.A method for rapidly starting up a bus system that is operable to carrydata according to an IEEE 1394, the IEEE 1394 standard defining a datatransmission protocol and a start up operation that includes a debouncedelay sequence, a speed negotiation sequence, a bus initializationsequence, and a training and symbol synchronization sequence, the methodcomprising: performing the bus initialization sequence using the bussystem that is operable to carry data according to the data transmissionprotocol of the IEEE 1394; and carrying data according to the datatransmission protocol of the IEEE 1394 standard using the bus systemafter performing the bus initialization sequence without performing thedebounce delay sequence.
 14. The method of claim 13, wherein carryingdata comprises carrying data without performing the speed negotiationsequence.
 15. The method of claim 13, wherein carrying data comprisescarrying data between a controller and a controlled device, thecontrolled device requiring the bus system to commence the carrying ofdata in less than 500 milliseconds from a time when the bus systemstarts to perform a device initialization sequence.
 16. The method ofclaim 13, wherein carrying data comprises carrying data between acontroller and a controlled device, the controlled device requiring thebus system to commence the carrying of data in approximately 100microseconds from a time when the bus system starts to perform a deviceinitialization sequence.
 17. The method of claim 13, wherein the bussystem is operable to perform the debounce delay sequence inapproximately 320 milliseconds and the speed negotiation sequence inapproximately 84 milliseconds to approximately 168 milliseconds.
 18. Themethod of claim 13, and further comprising performing the training andsymbol synchronization sequence before carrying data using the bussystem.
 19. The method of claim 13, wherein carry data comprisescarrying data without performing the speed negotiation sequence, and thebus system is operable to perform the debounce delay sequence inapproximately 320 milliseconds and the speed negotiation sequence inapproximately 84 milliseconds to approximately 168 milliseconds.
 20. Themethod of claim 13, and further comprising: performing the training andsymbol synchronization sequence using the bus system before carrying thedata; performing a device initialization sequence using the bus system;and wherein the bus system is operable to perform the debounce delaysequence in approximately 320 milliseconds and the speed negotiationsequence in approximately 84 milliseconds to approximately 168milliseconds.